The _a_c_c_t_c_v_t command is used to convert accounting data from one format to
another. The data can come from a file or stdin (such as when used as an
audit filter) and similarly can be written to another file or stdout.
Both SGI extended accounting and standard SVR accounting formats are
supported. In addition, output can be in the form of human-readable
text, similar to that produced by _s_a_t__i_n_t_e_r_p_r_e_t(1M).
Some input formats may contain data records that are not related to
accounting (such as system audit information in the extended accounting
formats). These records will not be contained in the reformatted output.
However, they can be copied verbatim to stdout in case _a_c_c_t_c_v_t is being
used together with other tools that may need that information. See
_a_u_d_i_t__f_i_l_t_e_r_s(5) and the Examples section below for information on how
this might work with the System Audit Trail.
OOOOPPPPTTTTIIIIOOOONNNNSSSS
_----_iiii Read input data as the second or later stage in a pipeline of audit
filters. Equivalent to specifying "_----_----_iiii_nnnn_pppp_uuuu_tttt______ssss_oooo_uuuu_rrrr_cccc_eeee _----",
"_----_----_iiii_nnnn_pppp_uuuu_tttt______ffff_oooo_rrrr_mmmm_aaaa_tttt _eeee_xxxx_tttt_aaaa_cccc_cccc_tttt_6666_...._5555", and "_----_----_iiii_nnnn_pppp_uuuu_tttt______nnnn_oooo_hhhh_eeee_aaaa_dddd_eeee_rrrr".
_----_oooo Run in "filter" mode: all input is copied unchanged to stdout, with
the exception that a file header will be discarded. This option
cannot be specified if "_----_----_oooo_uuuu_tttt_pppp_uuuu_tttt______dddd_eeee_ssss_tttt_iiii_nnnn_aaaa_tttt_iiii_oooo_nnnn _----" was also specified.
_----_qqqq Suppresses warning messages (usually concerning invalid record
types) to stderr.
_----_vvvv When used with the _tttt_eeee_xxxx_tttt output format, this specifies that audit
information not related to accounting should be included in the
Some accounting software may read extended accounting records directly
from the System Audit Trail (SAT) using "audit filters" (see
_a_u_d_i_t__f_i_l_t_e_r_s(5) for more details on this technique). Software that does
this and that was designed for an earlier release of IRIX may in many
cases still be able to run on more recent releases of IRIX by using
_a_c_c_t_c_v_t as an audit filter. For example, suppose a program that was used
to process IRIX 6.2 extended accounting records was invoked by placing
its command line in the file _////_eeee_tttt_cccc_////_cccc_oooo_nnnn_ffff_iiii_gggg_////_ssss_aaaa_tttt_dddd_...._ffff_iiii_llll_tttt_eeee_rrrr_----_1111. In IRIX 6.5 this
same software could be used in the same way by adding _a_c_c_t_c_v_t as an
additional filter that occurs _b_e_f_o_r_e the accounting software. To do so,
the file _////_eeee_tttt_cccc_////_cccc_oooo_nnnn_ffff_iiii_gggg_////_ssss_aaaa_tttt_dddd_...._ffff_iiii_llll_tttt_eeee_rrrr_----_0000 could be created, containing:
If the system audit facility is being used for conventional audit
purposes in addition to collecting accounting data, it may be necessary
to pass unmodified audit data on to other filters via stdout as well as
writing reformatted data to a separate output file or accounting program.
_a_c_c_t_c_v_t provides the _----_oooo and _----_ffff options (or their long forms, _----_----_ffff_iiii_llll_tttt_eeee_rrrr and
_----_----_oooo_uuuu_tttt_pppp_uuuu_tttt______dddd_eeee_ssss_tttt_iiii_nnnn_aaaa_tttt_iiii_oooo_nnnn) for handling this situation. The _----_oooo option
instructs _a_c_c_t_c_v_t to copy all input data (except a file header, if
present) to stdout, where it can be read by a subsequent audit filter.
then the command "_////_uuuu_ssss_rrrr_////_bbbb_iiii_nnnn_////_mmmm_yyyy_aaaa_cccc_cccc_tttt _----_iiii _----_dddd_iiii_rrrr _////_aaaa_cccc_cccc_tttt" would be started in a
second process and it would receive IRIX 6.2-style extended accounting
records from _a_c_c_t_c_v_t via stdin. In the meantime, _a_c_c_t_c_v_t would still
continue to copy unmodified IRIX 6.5 audit records to stdout for use by
other filters. Notice that the command is enclosed in single quotes to
protect it from interpretation by the shell. In more complicated cases
it may be helpful to write a simple wrapper script for the second command